Personalized emergency evacuation plan

ABSTRACT

Embodiments of the present invention disclose a method, computer program product, and system for generating and transmitting a Personalized Emergency Evacuation Plan (PEEP). The computer receives an emergency condition real-time data from a plurality of building sensors, a tracking data of at least one user from a plurality of tracking sensors, a facility structural data from a facility database, and a stored user data from a user database for the at least one user. The computer generates a personalized emergency evacuation plan (PEEP) for the at least one user, wherein is a set of recommendations to put the user in the safest position, based on at least the emergency condition real-time data and the received stored user data. The computer transmits the PEEP to a user mobile device, wherein the user mobile device presents the PEEP to the at least one user.

BACKGROUND

The present invention relates generally to the field of buildingevacuation plans, and more particularly to generating a personalizedemergency plan for a user having a medical condition.

In the event of an emergency, some individuals may not be able to reacha safe place without aid or in a reasonable amount of time due to amedical condition which limits their cognitive or physical abilities. APersonal Emergency Evacuation Plan (PEEP) is a type of escape plan forthose individuals with medical conditions, for example, blindness,deafness, amputee, or asthma, which limit their abilities. People withmedical conditions can be limited by their condition as to how they canevacuate a building, reaching a safe location or following through withgeneric emergency evacuation procedures.

BRIEF SUMMARY

Additional aspects and/or advantages will be set forth in part in thedescription which follows and, in part, will be apparent from thedescription, or may be learned by practice of the invention.

Embodiments of the present invention disclose a method, computer programproduct, and system for generating and transmitting a PersonalizedEmergency Evacuation Plan (PEEP). The computer receives emergencycondition real-time data from a plurality of building sensors and thecomputer receives tracking data of at least one user from a plurality oftracking sensors. The emergency condition real-time data includes atleast one from the location of the emergency, alarms going off, and/orother data from any sensor within the building. The computer receivesfacility structural data from a facility database, wherein the facilitystructural data includes building layout, location of stairs, locationof exits, and any other stored data about the building. The computerreceives stored user data from a user database for the at least oneuser, wherein the stored user data includes a user age, a user gender, auser medical condition, and any other user data. The computer generatesa PEEP for the at least one user, wherein the PEEP is a set ofrecommendations to put the user in the safest position, based on atleast the emergency condition real-time data and the received storeduser data. The computer transmits the PEEP to a user mobile device,wherein the user mobile device presents the PEEP to the at least oneuser.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainexemplary embodiments of the present invention will be more apparentfrom the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a functional block diagram illustrating a system forgenerating and transmitting a Personal Emergency Evacuation Plan, inaccordance with an embodiment of the present invention.

FIGS. 2A and 2B are flowcharts depicting operational steps to generateand transmit a Personal Emergency Evacuation Plan within the environmentof FIG. 1, in accordance with an embodiment of the present invention.

FIG. 3 is a flowchart depicting operational steps from a perspective ofa first responder to obtain a user's Personal Emergency Evacuation Planwithin the environment of FIG. 1, in accordance with an embodiment ofthe present invention.

FIG. 4 is a flowchart depicting operational steps from a perspective ofa user that receives a Personal Emergency Evacuation Plan within theenvironment of FIG. 1, in accordance with an embodiment of the presentinvention.

FIG. 5 illustrates an example of a building layout, where the presentinvention can be implemented.

FIG. 6 is a block diagram of components of a mobile device of the systemfor receiving a Personal Emergency Evacuation Plan of FIG. 1, inaccordance with embodiments of the present invention.

FIG. 7 is a block diagram of components of a computing device of thesystem for generating and transmitting a Personal Emergency EvacuationPlan of FIG. 1, in accordance with embodiments of the present invention.

FIG. 8 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 9 depicts abstraction model layers according to an embodiment ofthe present invention.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of exemplaryembodiments of the invention as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the embodiments described hereincan be made without departing from the scope and spirit of theinvention. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used to enablea clear and consistent understanding of the invention. Accordingly, itshould be apparent to those skilled in the art that the followingdescription of exemplary embodiments of the present invention isprovided for illustration purpose only and not for the purpose oflimiting the invention as defined by the appended claims and theirequivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces unless the context clearly dictatesotherwise.

Reference will now be made in detail to the embodiments of the presentinvention, examples of which are illustrated in the accompanyingdrawings, wherein like reference numerals refer to like elementsthroughout.

Embodiments of the invention are generally directed to a system togenerate and transmit a Personal Emergency Evacuation Plan (PEEP) to auser. PEEP's are useful for individuals who have mobility impairments,sight impairments, hearing impairments, cognitive impairments, asthma,and other such medical conditions. PEEP's are also useful forindividuals who have short term injuries, temporary medical conditions,and are in the later stages of pregnancy. When an emergency, such as afire, an earthquake, a gas leak, or other such emergency, is detectedthe server retrieves stored building data, i.e. building layout, andreal-time building data. The building uses sensors to detect emergencyconditions within the building and the building can track the locationof users within the building. The data gathered by the building sensors,such as temperature, presence of a fire, and other such data, inreal-time is taken into consideration in the formation of the PEEP. Thesystem then identifies users at risk. The user's mobile device transmitspersonal information such as age, gender, medical conditions, and otherdata that the mobile device is able to collect. When a wearable deviceis present on the user, real-time biometric data can be obtained to aidin assessing the user's current condition. The server retrieves storeddata, for example, know medical conditions, physical limitations, orother stored medical data, corresponding to the user at risk. A riskanalysis program uses the retrieved data and the real-time data toperform a risk assessment for the at-risk user. A PEEP is generated bytaking into consideration the risk analysis and the user's currentconditions. The PEEP is transmitted to the user's mobile device eitherthrough an acoustic device or a graphical user interface. The user canaccept or reject the received PEEP. When the PEEP is rejected, a newPEEP will be generated. When the PEEP is accepted, the system willmonitor the user's movements and adjust the PEEP to account for changingconditions. First responders will be notified of the users PEEP and theuser's current location and conditions.

FIG. 1 is a functional block diagram illustrating a system forgenerating and transmitting a Personal Emergency Evacuation Plan (PEEP)100, in accordance with an embodiment of the present invention.

The system for generating and transmitting a PEEP 100 includes abuilding 120, a user mobile device 130, a first responder's device 140,and a server 150. The building 120, the user mobile device 130, thefirst responder's device 140, and the server 150 are able to communicatewith each other via a network 110.

Network 110 can be, for example, a local area network (LAN), a wide areanetwork (WAN) such as the Internet, or a combination of the two, and caninclude wired, wireless, or fiber optic connections. In general, network110 can be any combination of connections and protocols that willsupport communications between the building 120, the user mobile device130, the first responder's device 140, and the server 150, in accordancewith one or more embodiments of the invention.

The building 120 includes sensors 122 and a tracking sensor 124. Thebuilding 120 represents a structure that contains the sensors 122, whichcan be utilized during an emergency, such as a smoke detector, a carbonmonoxide detector, a thermostat, motion sensors, and other such sensors.The building 120 further includes the tracking sensor 124 which can usea global positioning system, WIFI tracking system, cameras, or othermeans to track users within the building 120, or any combinationthereof. The sensors 122 and the tracking sensor 124 provide thereal-time collected data to the emergency condition real-time module172, via the network 110.

The user mobile device 130 may be any type of mobile computing devicethat is capable of connecting to the network 110, for example, a smartphone or any programmable electronic device supporting the functionalityrequired by one or more embodiments of the invention. The user mobiledevice 130 may include internal and external hardware components, asdescribed in further detail below with respect to FIG. 6 or FIG. 7. Inother embodiments, the server 150 may operate in a cloud computingenvironment, as described in further detail below with respect to FIGS.8 and 9.

The user mobile device 130 may be connected to a wearable device 132,through for example, a BLUETOOTH connection. The wearable device 132 iscapable of detecting heartbeat, temperature, number of steps taken,number of calories burned, and other such biometric capabilities. Thedata collected by the wearable device 132 is transmitted by the usermobile device 130 to the user real-time condition module 170, via thenetwork 110.

The user mobile device 130 represents a computing device that include auser interface, for example, a graphical user interface 134. Thegraphical user interface 134 can be any type of application thatcontains the interface to receive a PEEP, input data to the PEEPapplication 160, receiving data from the PEEP application 160, and/ordisplay a PEEP, for example, the application can be a web application, agraphical application, an editing application or any other type ofapplication/program that allows a user to upload, change, delete, alter,or update data accessible to the PEEP application 160. The user mobiledevice 130 further includes an acoustic device 136 that is able to playan auditory PEEP. Furthermore, the acoustic device 136 is able toreceive verbal commands, instructions or other statements, from theuser, to indicate the user's condition.

The first responder's device 140 may be any type of computing devicethat is capable of connecting to network 110, for example, a laptopcomputer, tablet computer, netbook computer, personal computer (PC), adesktop computer, a smart phone, or any programmable electronic devicesupporting the functionality required by one or more embodiments of theinvention. The first responder's device 140 may include internal andexternal hardware components, as described in further detail below withrespect to FIG. 6 or FIG. 7. In other embodiments, the server 150 mayoperate in a cloud computing environment, as described in further detailbelow with respect to FIGS. 8 and 9.

The first responder's device 140 represents a computing device thatinclude a user interface, for example, a graphical user interface 142.The graphical user interface 142 can be any type of application thatcontains the interface to receive a PEEP, input data to the PEEPapplication 160, receiving data from the PEEP application 160, and/ordisplay a PEEP, for example, the application can be a web application, agraphical application, an editing application or any other type ofapplication/program that allows a user to upload, change, delete, alter,or update data accessible to the PEEP application 160.

The server 150 includes a communication module 152 and a PEEPapplication 160. The server 150 is able to communicate with the building120, the user mobile device 130, and the first responder's device 140,via the network 110. Server 150 may include internal and externalhardware components, as depicted and described in further detail belowwith reference to FIG. 7. In other embodiments, the server 150 mayinclude internal and external hardware components, as depicted anddescribed in further detail below with respect to FIG. 8, and operate ina cloud computing environment, as depicted in FIG. 9.

The server 150 includes a communication module 152. The communicationmodule 152 is capable of receiving and displaying data from the building120, the user mobile device 130, and the first responder's device 140,via the network 110. The communication module 152 is also capable oftransmitting and displaying data from the PEEP application 160 to theuser mobile device 130 and the first responder's device 140, via thenetwork 110. The communication module 152 is able to accomplish thiseither through the graphical user interfaces 134 and 142 or the acousticdevice 136 or any combination thereof.

The PEEP application 160 includes a facility database 162, a userdatabase 164, a first aid/survival database 166, a tracking module 168,a user real-time condition module 170, an emergency condition real-timemodule 172, a risk analysis module 174, and a PEEP generation module176.

The facility database 162, the user database 164, and the firstaid/survival database 166 are each data stores that store previouslyuploaded data. The facility database 162 stores data such as buildinglayout, location of stairwells, location of exits, and other such data.The facility database 162 also stores data from the sensors 122 whenthere is not an emergency as a baseline. The user database 164 storesdata such as age, gender, medical conditions, and other medical datathat was uploaded by the user. When a wearable device 132 is present,the user database 164 stores user biometric data from a non-emergency asa baseline. The first aid/survival database 166 stores data such asfirst aid knowledge and survival skills.

The tracking module 168 uses tracking data received from the trackingsensor 124 within building 120 and the user mobile device 130 todetermine the user location, location of other people in the vicinity ofthe user, and location of the emergency. The tracking data used by thetracking module 168 can be from a global positioning system, WIFItracking system, cameras, or other means to track users within thebuilding 120, or from tracking information received from the user mobiledevice 130, or any combination thereof. The tracking module 168 canconfirm the safety of a user by tracking their location against that ofthe first responder. The tracking module 168 can transmit the user'slocation to the first responder's device 140, via the network 110. Thetracking module 168 identifies user at risk from the emergency bycomparing the user current location to the location of the emergency.

The user real-time condition module 170 receives real-time data from theuser mobile device 130, such as location and user inputted information,via the network 110. The user real-time condition module 170 receivesdata from sensors in the user mobile device 130, such as anaccelerometer, tracking sensor, and/or other sensors. When a wearabledevice 132 is present, real-time data such as heartbeat, temperature,number of steps taken, number of calories burned, and other suchbiometric capabilities are transmitted to the user real-time conditionmodule 170, via the network 110. The user real-time condition module 170collects the real-time user data in order to determine the currentcondition of the user. The user real-time condition module 170 comparesthe real-time data received from the user mobile device 130 to the userdata stored in the user database 164 to determine the current conditionof the user. The user real-time condition module 170 is able to detectchanging user conditions through user inputs or if a wearable device 132is present, through changes in the data that is continuously collected.The user real-time condition module 170 can transmit the user currentcondition to the first responder's device 140, via the network 110.

The emergency condition real-time module 172 receives real-time datafrom the building 120, via the network 110. The real-time data from thebuilding 120 can be collected from the sensors 122. The emergencycondition real-time module 172 receives real-time data such as abuilding alarm going off, detection of a fire, detection of a poisonousleak, and other such emergency conditions. The emergency conditionreal-time module 172 uses the collected real-time data in order todetermine the current emergency condition. The emergency conditionreal-time module 172 determines the current emergency condition bycomparing the real-time data to data taken in a non-emergency stored inthe facility database 162. The sensors 122 determine the type ofemergency, for example, smoke detectors can detect the presence of afire or smoke, cameras can detect structural damage, and thermometerscan detect the presence of a fire in the walls or floor by a temperaturechange. The emergency condition real-time module 172 receives thedifferent type of data from the sensors 122, (the type of data isdependent on the type of sensor), wherein the emergency conditionreal-time module 172 is able to determine the type of emergency based onthe received data from the sensors 122. The emergency conditionreal-time module 172 is able to detect if emergency conditions arechanging from the real-time data it receives from the sensors 122. Theemergency condition real-time module 172 can transmit the currentemergency conditions to the first responder's device 140, via thenetwork 110.

The risk analysis module 174 uses the tracking module 168 to determine auser at risk. The risk analysis module 174 then uses the facilitydatabase 162, the user database 164, the first aid/survival database166, the user real-time condition module 170, and the emergencycondition real-time module 172 to determine a ranking of potentialactions the user can perform based on a risk analysis. The data from thefacility database 162 and the emergency condition real-time module 172are used to determine the safest location for the user to be during theemergency. The data from the user database 164 and the user real-timecondition module 170 are used to determine any pre-existing medicalconditions and any medical conditions that may have occurred due to theemergency. The first aid/survival database 166 is used to determine ifthe user can perform any first aid on themselves during the emergency.The risk analysis module 174 uses this data to provide plans of actionfor the PEEP generation module 176. If the user real-time conditionmodule 170 or the emergency condition real-time module 172 detectchanging conditions, the risk analysis module 174 will conduct a newrisk analysis. The new risk analysis is conducted by analyzing the mostrecent data collected by the user real-time condition module 170 and theemergency condition real-time module 172.

The PEEP generation module 176 uses the risk analysis determined by therisk analysis module 174 to generate PEEP's. A PEEP is a plan of actionfor the user which will direct them in the most optimal position, forexample, a safe location, easy access to first aid, farthest distancefrom the emergency, any action to direct the user to a safe location, orany combination thereof. The PEEP generation module 176 generates thePEEP, wherein the PEEP can be, for example, a map with directions, firstaid instructions, acoustic commands, and/or informing the user thelocation of the first responders. The PEEP generation module 176 usesthe information gathered by the risk analysis module 174 to determinethe safest plan of action for the user. Multiple PEEP's are generatedfor each user based on the ranking determined by the risk analysismodule 174. The PEEP generation module 176 transmits the PEEP to theuser mobile device 130 and the first responder's device 140, via thenetwork 110. The communication module 152 displays the PEEP to the usermobile device 130 and the first responder's device 140 through graphicaluser interfaces 134 and 142 and/or the acoustic device 136.

The tracking module 168 can further identify a second user in thevicinity of a disabled user. The PEEP generation module 176 generates aPEEP for the disabled user but transmits the PEEP to the second user.This allows for the PEEP generation module 176 to send PEEP withinstructions to help a disabled user to user in his/her vicinity.

FIGS. 2A and 2B represent the server 150 receiving and gathering datafrom the building 120 and the user mobile device 130 to generate a PEEPand transmitting the PEEP to the user mobile device 130 and the firstresponder's device 140.

FIG. 2A illustrates the steps for receiving and gathering data. Theemergency condition real-time module 172 detects an emergency conditionbased on the data transmitted from the sensors 122 (S200). Differenttypes of sensors 122 collect different types of sensor data, wherein theemergency condition real-time module 172 is able to determine the typeof emergency from the received data from the sensors 122. The emergencycondition real-time module 172 is able to determine the type ofemergency from the received data, for example, smoke detectors candetect the presence of a fire or smoke, cameras can detect structuraldamage and thermometers can detect the presence of a fire in the wallsor floor by a change in the sensed temperature (S202). The risk analysismodule 174 receives the facility structural data from the facilitydatabase 162 (S204). The risk analysis module 174 also receivesemergency data from the emergency condition real-time module 172 (S206).S204 and S206 are happening concurrently because the real-time andstored data are being received at the same time. The tracking module 168identifies a user at risk from the emergency by comparing the usercurrent location to the location of the emergency (S208). The riskanalysis module 174 receives stored user data, for the user that wasidentified as being at risk, from the user database 164 (S210). The userreal-time condition module 170 receives real-time condition data fromthe user mobile device 130 and/or real-time data from the wearabledevice 132 (S212). S210 and S212 are happening concurrently because thereal-time and stored data are being received at the same time. The riskanalysis module 174 then conducts a risk assessment based on the datafrom the facility database 162, the user database 164, the trackingmodule 168, the user real-time condition module 170, and the emergencycondition real-time module 172 (S214). The PEEP generation module 176generates a PEEP based on the current data from the risk analysis module174 (S216).

FIG. 2B illustrates the steps for transmitting the PEEP. Thecommunication module 152 delivers the PEEP to the user mobile device 130and the first responder's device 140 (S218). The graphical userinterfaces 134 and 142 are able to display the PEEP and/or the acousticdevice 136 is able to provide auditory instructions that correspond tothe PEEP. The PEEP generation module 176 determines if the user acceptedthe PEEP (S220). When the user declines the PEEP, the PEEP generationmodule 176 generates a new PEEP based on the current data (S216). Whenthe user accepts the PEEP, the PEEP generation module 176 determines ifthe user is following the PEEP based on the tracking module 168 and theuser real-time condition module 170 (S222). When the user is notfollowing the PEEP, the risk analysis module 174 conducts another riskassessment based on current conditions (S214). When the user isfollowing the PEEP, the emergency condition real-time module 172continuously determines if the emergency conditions are changing (S224).When the emergency conditions are changing, the risk analysis module 174conducts another risk assessment based on current conditions (S214).When the current conditions are not changing, the tracking module 168determines if the user completed the PEEP by tracking the user locationin relation to the generated PEEP (S226). When the user does notcomplete the PEEP, the tracking module 168 tracks the user until theuser has completed the PEEP (S226). When the user has completed thePEEP, the emergency condition real-time module 172 determines if theemergency conditions are changing (S228). When the emergency conditionsare changing, the risk analysis module 174 conducts another riskassessment based on current conditions (S214). When the emergencyconditions are not changing, the tracking module 168 will confirm thesafety of the user from the first responders (S230).

FIG. 3 represents a first responder's device 140 receiving a user's PEEPfrom the server 150, via the network 110.

FIG. 3 illustrates the steps for a first responder receiving a user'sPEEP. The emergency condition real-time module 172 detects an emergencycondition based on the data transmitted from the sensors 122 (S300).Different types of sensors 122 collect different types of sensor data,wherein the emergency condition real-time module 172 is able todetermine the type of emergency from the received data from the sensors122. The emergency condition real-time module 172 is able to determinethe type of emergency from the received data, for example, smokedetectors can detect the presence of a fire or smoke, cameras can detectstructural damage and thermometers can detect the presence of a fire inthe walls or floor by a change in the sensed temperature (S302). Thetracking module 168 identifies the first responder's location, using atracking component, for example, global positioning system, found in thefirst responder's device 140 (S304). The communication module 152transmits real-time emergency data from the emergency conditionreal-time module 172 to the first responder's device 140 to be displayedon the graphical user interface 142 (S306). The communication module 152transmits the user's location from the tracking module 168 to the firstresponder's device 140 (S308). The graphical user interface 142 is ableto display the user's location. The communication module 152 transmitsthe user's real-time condition data from the user real-time conditionmodule 170 to the first responder's device 140 (S310). The graphicaluser interface 142 is able to display the user real-time condition data.The communication module 152 transmits the user's PEEP to the firstresponder's device 140 (S312). The graphical user interface 142 is ableto display the PEEP. The PEEP generation module 176 determines if theuser is following the PEEP (S314). When the user is not following thePEEP, the communication module 152 transmits the user's tracked locationfrom the tracking module 168 to the first responder's device 140 (S308).When the user is following the PEEP, the emergency condition real-timemodule 172 determines if the emergency conditions are changing (S316).When the emergency conditions are changing, the communication module 152transmits the user's continuously tracked location from the trackingmodule 168 to the first responder's device 140 (S308). When theemergency conditions are not changing, the tracking module 168 canconfirm the safety of the user with the first responder (S318).

FIG. 4 represents a user in an emergency receiving a PEEP from theserver 150 on the user mobile device 130, via the network 110.

FIG. 4 illustrates the steps for a user to receive a PEEP. The userinputs user data into the user mobile device 130 either by manuallyinputting the information via the graphical user interface 134 and/or byverbally inputting the information via the acoustic device 136 (S400).The user mobile device 130 transmits the current user conditions fromuser inputs and/or from the wearable device 132, when present, to theuser real-time condition module 170 (S402). The user mobile devicereceives PEEP recommendations from the PEEP generation module 176(S404). The graphical user interface 134 displays the visual PEEP and/orthe acoustic device 136 plays an acoustic PEEP (S406). The user mobiledevice 130 determines if the user accepts the PEEP either throughaccepting it on the graphical user interface 134 and/or verballyaccepting it through the acoustic device 136 (S408). When the user doesnot accept the PEEP, the user mobile device 130 transmits the currentuser conditions from user inputs and/or from the wearable device 132,when present, to the user real-time condition module 170 (S402).

When the user accepts the PEEP, the PEEP generation module 176determines if the user is carrying out the PEEP based on the trackingmodule 168 and the user real-time condition module 170 (S410). When theuser is not carrying out the PEEP, the user mobile device 130 transmitsthe current user conditions from user inputs and/or from the wearabledevice 132, when present, to the user real-time condition module 170(S402).

When the user is carrying out the PEEP, the emergency conditionreal-time module 172 and the user real-time condition module 170determine if the current emergency conditions are changing (S412). Whenthe current conditions are changing, the user mobile device 130transmits the current user conditions from user inputs and/or from thewearable device 132, when present, to the user real-time conditionmodule 170 (S402). When the current conditions are not changing, thetracking module 168 determines if the user completed the PEEP bytracking the user location in relation to the generated PEEP (S414).When the user is not completing the PEEP, the tracking module 168 tracksthe user until the user has completed the PEEP (S414). When the user hascompleted the PEEP, the emergency condition real-time module 172 and theuser real-time condition module 170 determine if the current conditionsare changing (S416). When the current conditions are changing, thecommunication module 152 transmits current user conditions from userinputs into the user mobile device 130 and/or from the wearable device132, when present, to the user real-time condition module 170 (S402).When the current conditions are not changing, the tracking module 168can confirm the safety of the user with the first responder (S418).

FIG. 5 represents a situation in which the system for generating andtransmitting a PEEP 100 is used.

FIG. 5 illustrates a building that includes floors F1 through F4 andfloor F4 with apartments/office units A1 through A12, stairs S1, andelevator E1. The following exemplary situation illustrates the disclosedinvention being utilized. There is a user in apartment A4 who is elderlyand uses a walker. The sensors 122 detect a fire in apartment A1. Therisk analysis module 174 and the PEEP generation module 176 receivestructural data from the facility database 162, user data from the userdatabase 164, assistance data from the first aid/survival database 166,tracking data from the tracking module 168, real-time condition datafrom the user real-time condition module 170, and real-time emergencydata from the emergency condition real-time module 172.

The PEEP generation module 176 generates a PEEP based on the receiveddata. The user mobile device 130 of the elderly person at risk receivesthe PEEP via the graphical user interface 134 and/or the acoustic device136. The elderly person accepts the PEEP via the graphical userinterface 134 and/or the acoustic device 136 of the user mobile device130. The PEEP recommends the elderly person to take the elevator E1,when available, instead of the stairs S1 due to his/her mobilityimpairment. A different recommendation can be made when the elevator E1is not available or accessible. The elderly person is tracked by thetracking module 168 leaving apartment A4 and moving toward the elevatorE1. The user real-time condition module 170 detects that he/she ishaving breathing difficulties based on the heartbeat data from thewearable device 132. A new risk analysis is performed by the riskanalysis module 174 and a new PEEP is generated by the PEEP generationmodule 176. The elderly person receives an alert via the graphical userinterface 134 and/or the acoustic device 136 on the user mobile device130 that a new PEEP has been received. The elderly person accepts thenew PEEP via the graphical user interface 134 and/or the acoustic device136. The new PEEP recommends that the elderly person walk to apartmentA7 and wait for first responders to arrive. Apartment A7 is the farthestapartment from the fire in apartment A1. The tracking module 168 detectsthat first responders are in apartment A7 with the elderly person. Theelderly person is safe and the PEEP is complete.

The following is another exemplary situation that illustrates thedisclosed invention being utilized, similar to the situation previouslydescribed, in accordance with FIG. 5. The user in apartment A4 isvisually impaired. The sensors 122 detect a fire in apartment A1. Thetracking module 168 identifies a user in apartment A9 who does not haveany medical conditions. The risk analysis module 174 and the PEEPgeneration module 176 receive structural data from the facility database162, user data from the user database 164, assistance data from thefirst aid/survival database 166, tracking data from the tracking module168, real-time condition data from the user real-time condition module170, and real-time emergency data from the emergency condition real-timemodule 172.

The PEEP generation module 176 generates a PEEP based on the receiveddata. The user mobile device 130 of the visually impaired person at riskreceives the PEEP, and plays the auditory PEEP via the acoustic device136. The user mobile device 130 of the user in apartment A9 who is notat risk receives the PEEP via the graphical user interface 134 and/orthe acoustic device 136. The PEEP recommends that the user in apartmentA9 who is not at risk escort the visually impaired person in apartmentA4 down the stairs S1. When the stairs S1 are not available oraccessible, a different recommendation would be made. The visuallyimpaired person and the user not at risk are tracked by the trackingmodule 168 leaving apartment A4 and moving down the stairs S1. Thetracking module 168 detects that the visually impaired person and theuser not at risk have exited the building safely. The PEEP is complete.

FIG. 6 is a block diagram of components of the user mobile device 130and/or the first responder's device 140 for invoking a user environmentbased on a device cover, in accordance with an embodiment of the presentinvention. In an exemplary embodiment, the user mobile device 130 and/orthe first responder's device 140 include one or more processors 810, oneor more computer-readable RAMs 812, one or more computer-readable ROMs814, and one or more computer-readable tangible storage devices 818 onone or more buses 816. One or more operating systems 830, one or moreapps or programs 832, and one or more user environment definitions 834are stored on the one or more computer-readable tangible storage devices818 for execution by one or more of the processors 810 via one or moreof the RAMs 812 (which typically include cache memory). In theillustrated embodiment, each of the computer-readable tangible storagedevices 818 is a semiconductor storage device such as ROM 814, EPROM,flash memory or any other computer-readable tangible storage device thatcan store a computer program and digital information. Alternatively,each of the computer-readable tangible storage devices 818 is a magneticdisk storage device of an internal hard drive.

The user mobile device 130 and/or the first responder's device 140 alsoincludes a read/write (R/W) interface 822, for example, a USB port, toread from and write to external computing devices or one or moreportable computer-readable tangible storage devices such as a CD-ROM,DVD, memory stick, magnetic disk, optical disk or semiconductor storagedevice. The apps and programs 832 and the user environment definitions834 can be stored on the external computing devices or one or more ofthe portable computer-readable tangible storage devices, read via theR/W interface 822 and loaded onto the computer-readable tangible storagedevice 818.

The user mobile device 130 and/or the first responder's device 140 alsoincludes a network adapter or interface 820, such as a TCP/IP adaptercard or wireless communication adapter (such as a 4G wirelesscommunication adapter using OFDMA technology). The apps and programs 832and the user environment definitions 834 can be downloaded to the usermobile device 130 and/or the first responder's device 140 from anexternal computer or external storage device via a network (for example,the Internet, a local area network, a wide area network, or a wirelessnetwork) and network adapter or interface 820. From the network adapteror interface 820, the apps and programs 832 and the user environmentdefinitions 834 are loaded into computer-readable tangible storagedevice 818. The network may comprise copper wires, optical fibers,wireless transmission, routers, firewalls, switches, gateway computersand/or edge servers.

The user mobile device 130 and/or the first responder's device 140 alsoincludes a touch screen 826, a camera 836, sensors 828, for example,touch screen sensors and magnetically sensitive circuits, and devicedrivers 824 to interface to touch screen 826 for imaging, to sensors 828for pressure sensing of alphanumeric character entry and user selectionsand for detecting magnetic flux and polarity. The device drivers 824,R/W interface 822 and network adapter or interface 820 comprise hardwareand software (stored in computer-readable tangible storage device 818and/or ROM 814).

It should be appreciated that FIG. 6 provides only an illustration ofone implementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

Based on the foregoing, a computer system, method and program producthave been disclosed for selecting a user environment based on a devicecover. However, numerous modifications and substitutions can be madewithout deviating from the scope of the present invention. Therefore,the present invention has been disclosed by way of example and notlimitation.

FIG. 7 depicts a block diagram of components of the user mobile device130 and/or the first responder's device 140 of the system for generatingand transmitting a PEEP 100 of FIG. 1, in accordance with an embodimentof the present invention. It should be appreciated that FIG. 7 providesonly an illustration of one implementation and does not imply anylimitations with regard to the environments in which differentembodiments may be implemented. Many modifications to the depictedenvironment may be made.

The user mobile device 130 and/or the first responder's device 140and/or the server 150 may include one or more processors 902, one ormore computer-readable RAMs 904, one or more computer-readable ROMs 906,one or more computer readable storage media 908, device drivers 912,read/write drive or interface 914, network adapter or interface 916, allinterconnected over a communications fabric 918. The network adapter 916communicates with a network 930. Communications fabric 918 may beimplemented with any architecture designed for passing data and/orcontrol information between processors (such as microprocessors,communications and network processors, etc.), system memory, peripheraldevices, and any other hardware components within a system.

One or more operating systems 910, and one or more application programs911, for example, the PEEP application 160 (FIG. 1), are stored on oneor more of the computer readable storage media 908 for execution by oneor more of the processors 902 via one or more of the respective RAMs 904(which typically include cache memory). In the illustrated embodiment,each of the computer readable storage media 908 may be a magnetic diskstorage device of an internal hard drive, CD-ROM, DVD, memory stick,magnetic tape, magnetic disk, optical disk, a semiconductor storagedevice such as RAM, ROM, EPROM, flash memory or any othercomputer-readable tangible storage device that can store a computerprogram and digital information.

The user mobile device 130 and/or the first responder's device 140and/or the server 150 may also include a R/W drive or interface 914 toread from and write to one or more portable computer readable storagemedia 926. Application programs 911 on the user mobile device 130 and/orthe first responder's device 140 and/or the server 150 may be stored onone or more of the portable computer readable storage media 926, readvia the respective R/W drive or interface 914 and loaded into therespective computer readable storage media 908.

The user mobile device 130 and/or the first responder's device 140and/or the server 150 may also include a network adapter or interface916, such as a Transmission Control Protocol (TCP)/Internet Protocol(IP) adapter card or wireless communication adapter (such as a 4Gwireless communication adapter using Orthogonal Frequency DivisionMultiple Access (OFDMA) technology). Application programs 911 on theuser mobile device 130 and/or the first responder's device 140 and/orthe server 150 may be downloaded to the computing device from anexternal computer or external storage device via a network (for example,the Internet, a local area network or other wide area network orwireless network) and network adapter or interface 916. From the networkadapter or interface 916, the programs may be loaded onto computerreadable storage media 908. The network may comprise copper wires,optical fibers, wireless transmission, routers, firewalls, switches,gateway computers and/or edge servers.

The user mobile device 130 and/or the first responder's device 140and/or the server 150 may also include a display screen 920, a keyboardor keypad 922, and a computer mouse or touchpad 924. Device drivers 912interface to display screen 920 for imaging, to keyboard or keypad 922,to computer mouse or touchpad 924, and/or to display screen 920 forpressure sensing of alphanumeric character entry and user selections.The device drivers 912, R/W drive or interface 914 and network adapteror interface 916 may comprise hardware and software (stored on computerreadable storage media 908 and/or ROM 906).

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported, providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 8, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 8 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 9, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 8) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 9 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and PEEP application 96.

Based on the foregoing, a computer system, method, and computer programproduct have been disclosed. However, numerous modifications andsubstitutions can be made without deviating from the scope of thepresent invention. Therefore, the present invention has been disclosedby way of example and not limitation.

While the invention has been shown and described with reference tocertain exemplary embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the presentinvention as defined by the appended claims and their equivalents.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the one or more embodiment, the practical application ortechnical improvement over technologies found in the marketplace, or toenable others of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method for generating and transmitting aPersonalized Emergency Evacuation Plan (PEEP), the method comprising:receiving, by a computer, an emergency condition real-time data from aplurality of building sensors and receiving, by the computer, a trackingdata of at least one user from a plurality of tracking sensors, whereinthe emergency condition real-time data includes at least one from thelocation of the emergency, alarms going off, and/or other data from anysensor within the building; receiving, by the computer, a facilitystructural data from a facility database, wherein the facilitystructural data includes building layout, location of stairs, locationof exits, and any other stored data about the building; receiving, bythe computer, a stored user data from a user database for the at leastone user, wherein the stored user data includes a user age, a usergender, a user medical condition, and any other user data; generating,by the computer, a personalized emergency evacuation plan (PEEP) for theat least one user, wherein is a set of recommendations to put the userin the safest position, based on at least the emergency conditionreal-time data and the received stored user data; and transmitting, bythe computer, the PEEP to a user mobile device, wherein the user mobiledevice presents the PEEP to the at least one user.
 2. The method ofclaim 1, further comprising: determining, by the computer, a type ofemergency occurring within the building from the received emergencycondition real-time data, wherein the type of emergency is a fire, a gasand/or water leak, an earthquake, structural damage, and/or anyemergency situation; wherein the generating of the PEEP for the at leastone user is further based on the determined type of emergency.
 3. Themethod of claim 1, further comprising: identifying, by the computer, atleast one additional user from the received tracking data and thereceived emergency condition real-time data, wherein the at least oneuser at risk is located near the at least one user; in response toidentifying the at least one additional user, transmitting, by computer,the PEEP to a mobile device of the at least one additional user, whereinthe user mobile device presents the PEEP to the at least one additionaluser.
 4. The method of claim 1, further comprising: receiving, by thecomputer, a user real-time condition data from the user mobile device ofthe at least one user, wherein the user real-time condition dataincludes data collected from at least one sensor from within the usermobile device.
 5. The method of claim 4, further comprising: conducting,by the computer, a risk assessment of the at least one user based on theemergency condition real-time data, the user real-time condition data,the received stored user data, and the received stored facilitystructural data; wherein the generation of the PEEP is further based onthe risk assessment of the at least one user and the user real-timecondition data.
 6. The method of claim 1, further comprising:transmitting, by the computer, the PEEP of the at least one user to afirst responder device, wherein the first responder's device displaysthe PEEP.
 7. The method of claim 6, further comprising: confirming, bythe computer, the safety of the at least one user based on a location ofthe at least one user at risk in relation to a location of the firstresponder.
 8. The method of claim 1, further comprising: in response tothe PEEP being transmitted to the user mobile device, determining, bythe computer, whether the identified at least one user at risk hasaccepted the PEEP.
 9. The method of claim 8, further comprising: inresponse to the PEEP being accepted by the at least one user,determining, by the computer, whether the at least one user is followingthe PEEP; and in response to the PEEP being rejected by the at least oneuser and/or that the at least one user is not following the PEEP,generating, by the computer, a new PEEP based on the on at least theemergency condition real-time data, and the received stored user data.10. The method of claim 1, further comprising: determining, by thecomputer, whether the emergency conditions are changing, based on thereceived emergency condition real-time data.
 11. The method of claim 10,further comprising: in response to determining that the emergencyconditions are changing, generating, by the computer, a new PEEP basedon the on at least the emergency condition real-time data, and thereceived stored user data.
 12. A non-transitory computer program productfor generating and transmitting a Personalized Emergency Evacuation Plan(PEEP), the computer program product comprising: one or morenon-transitory computer-readable storage media and program instructionsstored on the one or more non-transitory computer-readable storagemedia, the program instructions comprising: receiving an emergencycondition real-time data from a plurality of building sensors andreceiving a tracking data of at least one user from a plurality oftracking sensors, wherein the emergency condition real-time dataincludes at least one from the location of the emergency, alarms goingoff, and/or other data from any sensor within the building; receiving afacility structural data from a facility database, wherein the facilitystructural data includes building layout, location of stairs, locationof exits, and any other stored data about the building; receiving astored user data from a user database for the at least one user, whereinthe stored user data includes a user age, a user gender, a user medicalcondition, and any other user data; generating a personalized emergencyevacuation plan (PEEP) for the at least one user, wherein is a set ofrecommendations to put the user in the safest position, based on atleast the emergency condition real-time data, and the received storeduser data; and transmitting the PEEP to a user mobile device, whereinthe user mobile device presents the PEEP to the at least one user. 13.The non-transitory computer program product of claim 12, furthercomprising: determining a type of emergency occurring within thebuilding from the received emergency condition real-time data, whereinthe type of emergency is a fire, a gas and/or water leak, an earthquake,structural damage, and/or any emergency situation; wherein thegenerating the PEEP for the at least one user is further based on thedetermined type of emergency.
 14. The non-transitory computer programproduct of claim 12, further comprising: receiving a user real-timecondition data from the user mobile device of the at least one user,wherein the user real-time condition data includes data collected fromat least one sensor from within the user mobile device; and conducting arisk assessment of the at least one user based on the emergencycondition real-time data, the user real-time condition data, thereceived stored user data, and the received stored facility structuraldata; wherein the generation of the PEEP is further based on the riskassessment of the at least one user and the user real-time conditiondata.
 15. The non-transitory computer program product of claim 12,further comprising: in response to the PEEP being transmitted to theuser mobile device, determining whether the identified at least one userat risk has accepted the PEEP; in response to the PEEP being accepted bythe at least one user, determining, whether the at least one user isfollowing the PEEP; and in response to the PEEP being rejected by the atleast one user and/or that the at least one user is not following thePEEP, generating a new PEEP based on the on at least the emergencycondition real-time data, and the received stored user data.
 16. Acomputer system for generating and transmitting a Personalized EmergencyEvacuation Plan (PEEP), the computer system comprising: one or morecomputer processors, one or more computer-readable storage media, andprogram instructions stored on one or more of the computer-readablestorage media for execution by at least one of the one or moreprocessors, the program instructions comprising: receiving an emergencycondition real-time data from a plurality of building sensors andreceiving a tracking data of at least one user from a plurality oftracking sensors, wherein the emergency condition real-time dataincludes at least one from the location of the emergency, alarms goingoff, and/or other data from any sensor within the building; receiving afacility structural data from a facility database, wherein the facilitystructural data includes building layout, location of stairs, locationof exits, and any other stored data about the building; receiving astored user data from a user database for the at least one user, whereinthe stored user data includes a user age, a user gender, a user medicalcondition, and any other user data; generating a personalized emergencyevacuation plan (PEEP) for the at least one user, wherein is a set ofrecommendations to put the user in the safest position, based on atleast the emergency condition real-time data, and the received storeduser data; and transmitting the PEEP to a user mobile device, whereinthe user mobile device presents the PEEP to the at least one user. 17.The computer system of claim 16, further comprising: determining a typeof emergency occurring within the building from the received emergencycondition real-time data, wherein the type of emergency is a fire, a gasand/or water leak, an earthquake, structural damage, and/or anyemergency situation; wherein the generating the PEEP for the at leastone user is further based on the determined type of emergency.
 18. Thecomputer system of claim 16, further comprising: receiving a userreal-time condition data from the user mobile device of the at least oneuser, wherein the user real-time condition data includes data collectedfrom at least one sensor from within the user mobile device; andconducting a risk assessment of the at least one user based on theemergency condition real-time data, the user real-time condition data,the received stored user data, and the received stored facilitystructural data; wherein the generation of the PEEP is further based onthe risk assessment of the at least one user and the user real-timecondition data.
 19. The computer system of claim 16, further comprising:in response to the PEEP being transmitted to the user mobile device,determining whether the identified at least one user at risk hasaccepted the PEEP; in response to the PEEP being accepted by the atleast one user, determining, whether the at least one user is followingthe PEEP; and in response to the PEEP being rejected by the at least oneuser and/or that the at least one user is not following the PEEP,generating a new PEEP based on the on at least the emergency conditionreal-time data, and the received stored user data.
 20. The computersystem of claim 16, further comprising: transmitting the PEEP of the atleast one user to a first responder device, wherein the firstresponder's device displays the PEEP; confirming the safety of the atleast one user based on a location of the at least one user at risk inrelation to a location of the first responder.